Skip to content

[PULP-1776] Optimize upload_time and provenance in PyPI APIs#1244

Merged
jobselko merged 1 commit into
pulp:mainfrom
jobselko:perf_change
Jun 4, 2026
Merged

[PULP-1776] Optimize upload_time and provenance in PyPI APIs#1244
jobselko merged 1 commit into
pulp:mainfrom
jobselko:perf_change

Conversation

@jobselko
Copy link
Copy Markdown
Member

related to #1242, #1243

📜 Checklist

  • Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
  • A changelog entry or entries has been added for any significant changes
  • Follows the Pulp policy on AI Usage
  • (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

@jobselko jobselko self-assigned this May 21, 2026
@jobselko jobselko force-pushed the perf_change branch 2 times, most recently from 002c244 to fcd3b39 Compare May 21, 2026 15:07
@jobselko
Copy link
Copy Markdown
Member Author

Copy of pulp/pulp-service#1227

@jobselko jobselko changed the title Optimize Simple API upload_time and provenance [PULP-1776] Optimize Simple API upload_time and provenance May 27, 2026
Copy link
Copy Markdown
Member

@dkliban dkliban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've been running this change in production for 10 days and have seen significant reduction in load on the database. Let's merge this change.

@jobselko jobselko force-pushed the perf_change branch 2 times, most recently from ed36dc5 to dd21f4a Compare June 4, 2026 13:17
@jobselko jobselko force-pushed the perf_change branch 2 times, most recently from 2eba325 to c15a507 Compare June 4, 2026 13:19
@jobselko jobselko changed the title [PULP-1776] Optimize Simple API upload_time and provenance [PULP-1776] Optimize upload_time and provenance in PyPI APIs Jun 4, 2026
@jobselko jobselko marked this pull request as ready for review June 4, 2026 13:33
@jobselko jobselko merged commit 43f1bf0 into pulp:main Jun 4, 2026
14 checks passed
@patchback
Copy link
Copy Markdown

patchback Bot commented Jun 4, 2026

Backport to 3.27: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 43f1bf0 on top of patchback/backports/3.27/43f1bf08100f708dd84e4422919293b37f5317dc/pr-1244

Backporting merged PR #1244 into main

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it:
    $ git remote add upstream https://github.com/pulp/pulp_python.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code:
    $ git fetch upstream
    $ git checkout -b patchback/backports/3.27/43f1bf08100f708dd84e4422919293b37f5317dc/pr-1244 upstream/3.27
  4. Now, cherry-pick PR [PULP-1776] Optimize upload_time and provenance in PyPI APIs #1244 contents into that branch:
    $ git cherry-pick -x 43f1bf08100f708dd84e4422919293b37f5317dc
    If it'll yell at you with something like fatal: Commit 43f1bf08100f708dd84e4422919293b37f5317dc is a merge but no -m option was given., add -m 1 as follows instead:
    $ git cherry-pick -m1 -x 43f1bf08100f708dd84e4422919293b37f5317dc
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR [PULP-1776] Optimize upload_time and provenance in PyPI APIs #1244 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub:
    $ git push origin patchback/backports/3.27/43f1bf08100f708dd84e4422919293b37f5317dc/pr-1244
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@patchback
Copy link
Copy Markdown

patchback Bot commented Jun 4, 2026

Backport to 3.30: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.30/43f1bf08100f708dd84e4422919293b37f5317dc/pr-1244

Backported as #1249

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@jobselko jobselko deleted the perf_change branch June 4, 2026 17:56
jobselko added a commit that referenced this pull request Jun 4, 2026
…00f708dd84e4422919293b37f5317dc/pr-1244

[PR #1244/43f1bf08 backport][3.30] [PULP-1776] Optimize upload_time and provenance in PyPI APIs
jobselko added a commit that referenced this pull request Jun 5, 2026
[PULP-1776] Optimize upload_time and provenance in PyPI APIs

(cherry picked from commit 43f1bf0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants